home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
QRZ! Ham Radio 3
/
QRZ Ham Radio Callsign Database - Volume 3.iso
/
digests
/
tcp
/
930268.txt
< prev
next >
Wrap
Internet Message Format
|
1994-06-04
|
4KB
Date: Fri, 15 Oct 93 04:30:01 PDT
From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
Errors-To: TCP-Group-Errors@UCSD.Edu
Reply-To: TCP-Group@UCSD.Edu
Precedence: Bulk
Subject: TCP-Group Digest V93 #268
To: tcp-group-digest
TCP-Group Digest Fri, 15 Oct 93 Volume 93 : Issue 268
Today's Topics:
Packet Standards
Undeliverable Mail
Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".
We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party. Your mileage may vary. So there.
----------------------------------------------------------------------
Date: Thu, 14 Oct 1993 14:35:44 -0600 (MDT)
From: William Ti Baggett <wbaggett@nmsu.edu>
Subject: Packet Standards
To: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
> Date: Wed, 13 Oct 93 11:44:57 BST
> From: eeyimkn@unicorn.ccc.nottingham.ac.uk (Mike Knell)
> Subject: Packet Standards
> To: tcp-group@ucsd.edu
>
> (Copy to: tcp-group@ucsd.edu, rec.radio.amateur.digital.misc, AUTHOR@WW)
>
> Hi people,
> At the recent UK Sysop's meeting, it was decided that it was time to
> start working towards a unified system for the publication of the
> various standards used in packet. I, for my sins, have been given this
> job :-)
>
> At the moment, it can be difficult or impossible to find those
> standards documents that do exist for packet radio, as they have
> either never been written or are tucked away on obscure FTP archives..
> When a new software author wants to find out how the forwarding
> protocols work, and the real nitty-gritty such as "how many characters
> may a BID have?" it can be impossible to find out. It's a shame, as
> this will only breed lots of new mutually incompatible systems. We've
> seen the beginning of this already with the FBB/NNA forwarding thing,
> and the BID question provoked a huge flamewar recently on the UK
> network.. :-(
>
I agree with this 100%!!! A few days ago I mailed out a request for the
protocol specifications for Netrom/Thenet for a paper I am writing for
school. So far I've had 14 replies, all but one saying that they want to
read my paper and one reply telling me to look at NOSintro and NOSVIEW.
I have also been told that the Computer Networking Conference papers are
worth looking into, but there's not much ham radio stuff in a university
library (besides QST's back into the twenties).
Without our packet protocols written down in stone, how is anyone going to
develope more software? I'm finding it hard just to write a paper. So far
its the GRINOS manual, Comer's Internetworking with TCP/IP book,
Tannenbaum's (sp?) networks book, and a copy of the AX.25 spec that I've
got.
Again, if anyone knows where I can find some information, I'd greatly
appreciate it. A search for 'netrom' in our library just results in the
computerized card catalog letting out some chuckles.
73,
Tim
********************************************************************
Tim Baggett, AA5DF Electrical Engineering Student
New Mexico State University
Internet: WBAGGETT@DANTE.NMSU.EDU
AMPR: AA5DF@NMSUGW.AMPR.ORG US Snail: 1970 Buchanan Avenue
Twisted Pair: (505) 523-6829 Las Cruces, NM 88001
********************************************************************
------------------------------
Date: Thu, 14 Oct 93 12:48:06 -0400
From: NDHM X400 </G=X400/S=NDHM/O=GTEGOVSYS/PRMD=GTEGS/ADMD=TELEMAIL/C=US/@gtespace.ndhm.gtegsc.com>
Subject: Undeliverable Mail
To: TCP-Group@UCSD.Edu
Message: TCP-Group Digest V93 #267
Sent: Thu, Oct 14, 1993 11:47 AM
To: Ross Jr Charlie
On Server: NDHM 6
Date: Thu, Oct 14, 1993 12:49 PM
Reason: Could not be delivered because the destination Microsoft Mail server
could not be found.
------------------------------
End of TCP-Group Digest V93 #268
******************************
******************************